Cost Analysis for March 2024 Site Plans and Overage Protection Changes

#1

To help people at the University of Michigan know when to move to a larger website plan, as well as understand the effects of the upcoming March Site Plans limit changes and overage protection changes, I created a cost analysis spreadsheet. Make a copy, enter your organization’s details on the first sheet, then view the results on the second sheet.

If anyone finds something that is incorrect/broken or has suggestions for improvements, please let me know.

This link will always take you to the latest version of the spreadsheet:
https://websites.umich.edu/~markmont/public/pantheon-cost-analysis/

Here is a screenshot of the results for a typical for-profit organization paying annually by credit card:

image
image.png2740×1958 346 KB

#2

Maybe @mckenna.regets can help here, but in the information shown here and detailed in the notice from Pantheon, there appear to only be changes to the “Site Visits” limits. I am assuming that this translates to the “Visits” metric in the dashboard. There is no mention of any change to the Pages Served limit. Does the lack of mention of Pages Served mean there are no changes to that limit?

1 Like
#3

That’s what I’ve been assuming, but it would be good to get confirmation from Pantheon.

1 Like
#4

Thanks for the tag in @aaron! I am going to share your question with our team @markmont.umich.edu! Will let you know what they say :slightly_smiling_face:

#5

I’d like us to make a Docs page with guidance on when and how to downgrade plans: https://github.com/pantheon-systems/documentation/issues/8904 let’s move discussion there.

#6

An updated version of the spreadsheet (version 1.1) is now available at

https://websites.umich.edu/~markmont/public/pantheon-cost-analysis/

If you have version 1.01 or 1.0, please go to the URL above and make a new copy since version 1.1 corrects an error with Basic plan pricing and it should now find the lowest cost plan in all circumstances.

#7

Thanks Mark! I’m going to close this issue here.

#8